CVE-2021-47113
Btrfs inode reference vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injection stress uncovered a problem where we'd leave a dangling inode ref if we failed during a rename_exchange. This happens because we insert the inode ref for one side of the rename, and then for the other side. If this second inode ref insert fails we'll leave the first one dangling and leave a corrupt file system behind. Fix this by aborting if we did the insert for the first inode ref.
INFO
Published Date :
March 15, 2024, 9:15 p.m.
Last Modified :
March 13, 2025, 7:36 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update the affected Linux kernel packages.
- Reboot the system after the update.
Public PoC/Exploit Available at Github
CVE-2021-47113 has a 1 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2021-47113.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2021-47113 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2021-47113
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Ini adalah repository kumpulan CVE v.5
allcve cve cvelist newcve
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2021-47113 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2021-47113 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 13, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE CWE-416 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:5.13:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.13:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.13:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.13:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 from (excluding) 5.12.10 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (excluding) 5.10.43 Added Reference Type CVE: https://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5b Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5b Types: Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932 Added Reference https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5 Added Reference https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5b -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 28, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 14, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Mar. 15, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: btrfs: abort in rename_exchange if we fail to insert the second ref Error injection stress uncovered a problem where we'd leave a dangling inode ref if we failed during a rename_exchange. This happens because we insert the inode ref for one side of the rename, and then for the other side. If this second inode ref insert fails we'll leave the first one dangling and leave a corrupt file system behind. Fix this by aborting if we did the insert for the first inode ref. Added Reference kernel.org https://git.kernel.org/stable/c/0df50d47d17401f9f140dfbe752a65e5d72f9932 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/ff8de2cec65a8c8521faade12a31b39c80e49f5b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/dc09ef3562726cd520c8338c1640872a60187af5 [No types assigned]